Signal distribution interface

ABSTRACT

A user interface for a distributed antenna system (DAS) is provided. When executed by a processor, a signal distribution engine receives information about signals transported by the DAS and components of the DAS. The signal engine generates a signal set assignment user interface including a list of signals transported by the DAS and a signal set formation area for receiving a signal set. The signal engine also generates a signal distribution user interface that includes representations of signal sets, hardware components, and associations between hardware components. In response to receiving a request to associate the signal set with a specified hardware component, a command is output to configure a signal path so that signals in the signal set are provided to the specified hardware component.

CROSS-REFERENCE TO RELATED APPLICATION

A priority claim is hereby made to U.S. Provisional Application Ser. No. 61/844,057, filed Jul. 9, 2013 and titled “Signal Distribution Interface,” the contents of which are incorporated herein by reference.

BACKGROUND

A distributed antenna system (“DAS”) may be used to extend the coverage of a telecommunications system. DAS's may include various components, such as central access nodes, expansion nodes, and universal access points. Configuration of a DAS can be challenging. Because distribution of signals through a DAS can be complex, the DAS is typically planned in advance of the installation of the system. After installation, configuring a DAS can be challenging.

SUMMARY

The subject matter described herein includes methods and systems for controlling signals in a distributed antenna system via a signal distribution interface.

According to one example, the system includes a processor device and a non-transitory computer-readable medium on which a signal distribution engine is stored and which is executable by the processor device. The system is configured to receive information about signals transported by the DAS and about hardware components of the distributed antenna system that include a headend component and a remote component. The system is further configured to generate a signal set assignment user interface that includes a representation of signals transported by the system and a representation of signal sets. Each signal set includes one or more of the signals transported by the system. The system is further configured to generate a signal distribution user interface that includes representations of signal sets, hardware components, and associations between the signal sets and the hardware components. Responsive to receiving a command via the signal distribution user interface to associate a signal set with a specified hardware component, the system is configured to output a command to cause the distributed antenna system to configure a signal path so that signals in the signal set are provided to the specified hardware component.

According to another example, a non-transitory computer-readable medium has computer-executable instructions that, when executed by a computer having a display, enable the computer to display a graphical user interface. The graphical user interface is configured to display a signal set assignment user interface including a list of signals transported by a distributed antenna system (DAS) and a list of editable signal sets. Each signal set includes one or more of the signals transported by the DAS. The graphical user interface is further configured to display a signal distribution user interface. The signal distribution user interface includes a first grouping of one or more widgets, a second grouping of one or more widgets, and a list of signal sets. In the first grouping, each widget represents a headend component of the DAS. The second grouping of one or more widgets represents one or more remote units in the DAS that are associated with the headend components of the first grouping. The list of signal sets represents groups of signals to be transported in the DAS.

The details of one or more aspects and examples are set forth in the accompanying drawings and the description below. Other features and aspects will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting an example of a distributed antenna system according to one aspect of the present disclosure.

FIG. 2 is a block diagram depicting an example of a computing device according to one aspect of the present disclosure.

FIG. 3 depicts an example of a screen face of a landing page of a signal distribution user interface according to one aspect of the present disclosure.

FIG. 4 depicts an example of a screen face of a signal set assignment user interface for assigning signals to signal sets according to one aspect of the present disclosure.

FIG. 5 depicts an example of a screen face of a signal distribution user interface for associating signal sets to DAS components according to one aspect of the present disclosure.

FIG. 6 depicts an example of a screen face of a signal distribution user interface for selecting a signal set and highlighting corresponding associations to DAS components according to one aspect of the present disclosure.

FIG. 7 depicts an example of a screen face of a signal distribution user interface for selecting a DAS component and highlighting corresponding associations to signal sets according to one aspect of the present disclosure.

FIG. 8 depicts an example of a screen face of a quick reference i-link help guide according to one aspect of the present disclosure.

FIG. 9 depicts a process flow diagram for configuring a DAS according to one aspect of the present disclosure.

DETAILED DESCRIPTION

Certain aspects and features relate to a signal distribution interface usable for controlling signals in a distributed antenna system (DAS). The signal distribution interface can be a graphical user interface (GUI) by which the DAS can be configured and that provides a successful user experience from the perspective of the user with limited knowledge. The GUI can be generated by a computing device. The GUI may provide elements to allow a user to visualize a model of the system. The visual model of the DAS can allow the user to interact with the DAS hardware to plan the distribution of signal inputs to outputs. The signal distribution interface or GUI is made simple and intuitive by, for example, using visual cues and user action support to fill in gaps of a user's knowledge and provide guidance to facilitate the setup process. In response to inputs from a user received by the GUI, signal distribution in the DAS can be configured, changed, controlled, and established.

FIG. 1 is a block diagram of an example of a DAS 100 with a computing device 102 and communicatively coupled to signal sources 104, 106, such as base transceiver stations BTS-1, BTS-2, BTS-3, and BTS-4. The DAS 100 includes two central access nodes (CAN's) CAN-A 108, CAN-B 110 that are each a headend. The CAN's 108-110 can transceive signals between the signal sources 104 and universal access points (UAPs) directly or through expansion nodes over communication cables, optical fiber, or wirelessly. For example, CAN-A 108 can directly transceive signals with UAPs 112 and CAN-B 110 can directly transceive signals with UAPs 114. Alternatively, CAN-A 108 can indirectly transceive signals with UAPs 124 and 126 via transport expansion nodes (TENs), TEN-A 116 and TEN-B 118, respectively. CAN-B 110 can indirectly transceive signals with UAPs 128, 130 via TEN-C 120 and TEN-D 122, respectively. An example of a UAP includes a remote unit or a remote antenna unit. UAPs can each wirelessly communicate with mobile devices. In some aspects, UAPs may be positioned in a building or tunnel to extend wireless communication coverage.

A CAN may also route signals through other CANs to UAPs associated with the other CANs. For example, a signal from signal source BTS-1 associated with CAN-A 108 may be routed through CAN-B 110 to UAP-4 114. In some aspects, a separate switching and combining device (not shown) may be provided between a CAN and UAP and usable to interconnect the CAN and the UAP.

CAN-A 108 includes a controller 132 that can detect the existence of hardware, such as UAPs 112-114, 124-130, TENs 116-122, and other CANs 110 in the DAS 100 and certain information about the status of operation of the hardware. The controller 132 can be communicatively coupled to the computing device 102. The computing device 102 can receive information from the controller 132 and provide command signals to the controller 132 for controlling the distribution of signals between signal sources 104 and UAPs 112-114, 124-130. Information about signals transported by the DAS can be received from a source in the DAS or from a source outside of the DAS, such as a connected BTS. Information about signals transported by the DAS can be received either separately or in combination from the sources. For example, the controller 132 can respond to command signals from the computing device 102 by changing the UAPs 112-114, 124-130 that wirelessly transmit certain signals from a certain source 104 or 106.

FIG. 2 depicts a block diagram of an example of the computing device 102. Examples of the computing device 102 can include a computer, a server, a laptop, a mobile device, and a tablet computer. The computing device 102 includes a memory 202, a processor device 204, and an input/output (I/O) interface 206. The memory 202 may be a non-transitory computer-readable medium that tangibly stores executable code, such as a signal distribution engine 208. The signal distribution engine 208, when executed by the processor device 204, can cause the computing device 102 to perform actions. Examples of actions include generating a GUI for display by the display device 210 and providing commands to the controller 132, through the I/O interface.

FIGS. 3-8 depict examples of screen faces that may be generated by the processor device 204 executing the signal distribution engine 208.

FIG. 3 depicts an example of a landing page screen face 300 showing sets of signals 302 (e.g., S0 to S5) that can be associated with different hardware of a DAS. The same signal may be included in more than one signal set. The bottom portion 304 of the screen face 300 identifies the extension nodes (i.e., TENs) that are included in the DAS. In the example shown, TEN.5 is selected as illustrated by selection 306 and, once selected, UAPs associated with TEN.5 are displayed in the upper portion 308 of the screen face 300. Shown for each TEN and UAP is a freeform text description 314 that is the location of the TEN or UAP, but may include other information. Associated with each hardware component 312 (e.g., TEN and UAP) are the sets of signals 316 currently associated with the hardware component. In some aspects, a user can hover over a UAP using an input device, such as a mouse device, to receive freeform text information about the UAP. An indicator 318 associated with each UAP can indicate the condition of the UAP. Examples of indicators 318 can include: turned on and radiating signals (e.g., UAP.1 in the depicted example), connected but not radiating any signals (e.g., UAP.14 in the depicted example), and not radiating and associated with an alarm condition (e.g., UAP.6 in the depicted example). Alarm conditions and levels can also be represented on the screen face 300. For example, an alarm status 320 in the upper corner of the screen face 300 indicates different types of alarms and the number of alarms for each type. Also shown with respect to TEN.13 is an alarm indicator 322 representing that an alarm exists associated with TEN.13. Selecting the alarm indicator 322 may cause the computing device 102 to generate an alarm interface (not shown) through which a user can receive additional information about an alarm. The interface 300 also includes an “i-link” icon 324 that is selectable for displaying a help menu, a “link” icon 326 that is selectable for associating signal sets to hardware, and a “diskette” icon 328 that is selectable for saving signal set distribution changes.

As used herein, a “pane” can refer to a visual area within a user interface. A pane can have a rectangular or other two-dimensional shape and may or may not overlap with the area of other panes. A pane can display the output of, and allow input to, one or more computing processes. A pane can be displayed by a graphical display and can be manipulated with a pointer or other input device. Panes can be resized, moved, hidden, restored or closed. Panes can also include multiple graphical objects, such as a menu-bar, toolbar, controls, icons, and a working area. In the working area, a document, image, or other object can be displayed.

The signal distribution user interface shown in FIG. 3 can include multiple panes for displaying different types of information. Moreover, selecting items (e.g., representations of hardware components or signal sets) in a first pane can automatically change the information displayed in a second or third pane. The information displayed in the panes of the signal distribution user interface can be interrelated. A first list of signal sets transported by the system can be positioned in a first pane 302. A list of zones in the system and a second list of signals sets associated with each zone can be positioned in a second pane 304. At least one of the zones in the second pane can be selectable. For example, zone “Floor 6 Server Room” 306 is selected in FIG. 3. A list of remote units associated with a selected zone and a third list of signal sets associated with the selected zone can be positioned in a third pane 308. For example, the one or more UAPs associated with zone “Floor 6 Server Room” 306 and their associated signal sets can be displayed in third pane 308 in FIG. 3.

FIG. 4 is an example of a screen face by which a new signal set can be added. The screen face 400 can be accessed by selecting the “Add New Signal Set” option 238 on the screen face 300 of FIG. 3. FIG. 4 lists available signals 402 in the DAS 100 as detected by the controller 132. For each signal there is listed an identification 404, an operator 406, a band 408, a type 410, a sector 412, and MIMO information 414. A signal set can be created by selecting one or more signals from the list of available signals 402 and moving the signals using a mouse device, or otherwise, to the area corresponding to the assigned signal sets 416. For example, the user can drag the available signals and drop them into area 416 or can select one or more signals from the list of signals 402 and click arrows 418 to assign or unassign signals. A signal set name can be inputted in box 420 and the signal set saved using save interface 422, after which the signal set can appear above the list of signals 402 available for being assigned to a hardware component of the DAS 100.

Referring to FIG. 4, the signal set assignment user interface can include an available signals pane 402 that includes a representation of signals transported by the distributed antenna system that are available to be assigned to a signal set. For example, the available signals pane 402 displays four examples of available signals: 1.0.R1.1.1, 1.0.R1.1.2, 1.0.R1.2.1, and 1.0.R1.2.2. An assigned signals pane 416 can include a representation of signal sets transported by the distributed antenna system.

FIG. 5 is an example of a screen face 500 in which a signal set, S2, is being associated with UAP.1, which is associated with TEN.5. The signal set S2 can be associated with the UAP by a user dragging the representation 502 of the signal set to the representation 504 of the UAP listed at the top of the screen face 500 as being associated with TEN.5 506. As the representation 502 of signal set S2 is being dragged, representations 508 of some UAPs are highlighted a certain color (or another indicator) signifying that signal set S2 is already associated with the UAP, while representations 510 of other UAPs are highlighted with a different color (or other indicator) signifying that signal set S2 is not currently associated with the UAP. After the representation 502 of signal set S2 is dropped at the representation 504 of UAP.1 and the save icon is selected, the computing device 102 can output a command to the controller 132 to configure a path so that signals in signal set S2 are handled by UAP.1.

In other aspects, a signal set can be associated with a hardware component by left-clicking the representation of the hardware component to toggle the association of the signal set with that hardware component. A signal set can be associated with a TEN directly, which can cause the signal set to be associated with UAPs associated with that TEN. A signal set can be associated with a CAN directly, which can cause the signal set to be associated with TENs and UAPs associated with that CAN.

FIG. 6 depicts an example of a screen face in which signal set S2 is selected and, in response, the computing device causes the screen face to highlight the components (using a color or other indicator) of the hardware components (e.g., TENs and UAPs) with which the signal set is currently associated. For example, as shown in screen face 600, signal set S2 602 is selected causing UAP.15 and UAP.16 606 and TEN.5-TEN.10 604 to be highlighted, indicating the hardware components with which signal set S2 is currently associated.

FIG. 7 depicts an example of a screen face for selecting a hardware component (e.g., UAP, TEN, CAN) that highlights the associations that have been made with the selected hardware component to signal sets. For example, as shown in screen face 700, a hardware component, TEN.5, is selected as indicated by selection 702 and, in response, the computing device 102 highlights in the list of signal sets the signal sets currently associated with TEN.5, as indicated by selection 704.

FIG. 8 shows an example of a quick reference guide screen face. The screen face 800 may be generated by the signal distribution engine 208 in response to a user selecting the “i-link” icon 324 on a screen face such as the example screen face 300 shown in FIG. 3. In response to a selection of the “i-link” icon 324, the signal distribution engine 208 can provide a quick reference guide 802 with information displayed in an information portion 804 including but not limited to, for example, adding a new signal set and associating signal sets with DAS components.

In some aspects, additional visual cues can be generated on the screen face to provide the user with information and selectable options. Setting up a system model for the user can depend on the context in which the GUI is operating. Typically, the DAS GUI may be in an operational context or a setup context. When in operational context, the user can view current events and alarms, signal status, and update the software, among other things. When in setup context, the user can take such actions as editing alarm settings, setting modem parameters, and associating signal sources with destinations. Visual cues can indicate context to the user. The GUI may also allow the user to change context as needed, so the widgets can allow for one or more actions. One such action is a mouse click.

Other visual cues that may be included in setting up the user system model include providing crumb trails to the user or widgets representing various aspects of the DAS. Crumb trails, or “breadcrumbs,” may be used to indicate to the user how he or she arrived at a certain screen and allow him or her to go back to any previous step using a single action (i.e., click). Crumb trails may be displayed horizontally across the top of a screen face. Crumb trails may provide links back to each previous screen face the user navigated through to get to the current screen face or—in hierarchical user interface structures—the parent screen face of the current screen face. Crumb trails may provide a trail for the user to follow back to the starting or entry point. A greater-than sign (>), for example, may be used as a hierarchy separator, although other glyphs (such as >> or >) or graphical treatments may also be used. Crumb trails may include location- and attribute-type crumb trails. Location crumb trails may be static and display where the screen face is located in the hierarchy. Attribute crumb trails may provide information that categorizes the current screen face.

The visual cues may also include widgets or groupings of widgets. Widgets, or groups of widgets, may represent devices in the system either because they are well-known, look like the device in some way, and/or contain excellent labeling. Widgets may be grouped in a meaningful manner depending on the context in which the user is working. For example, when the user interface is operated in a setup context (e.g., during signal distribution definition), widgets indicating signal sources can be grouped together in one section of the screen while those indicating signal destinations can be grouped in another section.

Assisting the non-expert user so that appropriate user interactions with the system hardware can take place can depend on visual cues. Highlighting a widget or a set of widgets upon some action can prove helpful in many ways. For example, if the user has chosen to work in setup mode and clicks on a signal source widget, the GUI can highlight it and all widgets representing the receivers of the signal. So with a single action, the user can immediately learn the signal distribution from that single source. Another use of highlighting may be to alert the user that a device has a problem.

User assistance can also be given by providing high-level information about a device when the user hovers over a widget representing that device. User actions accepted by the device under the chosen context can be provided via a menu when the user takes some action, such as right-clicking.

In order for the user to retain a stable working model, placement of visual cues can depend on the overall GUI hierarchy. For example, information and actions that the user needs access to can be placed in the same location on every screen. Such placement may be at the outer edge of the screen, out of the “work” area.

For information and actions that are common across screens of the same context, visual cues can be placed in the same location on each of these screens for ease of locating the cues.

Actions that are allowed by the GUI may be either pointer operations or keyboard operations. Pointer operations can include mouse actions and touch actions. Each of these types of operation allow the user to do one or more of the following: left click, right click, double click, drag (i.e., to scroll), hover, drag and drop, select one or more widgets, zoom in, and zoom out.

Mouse operations may be accomplished using a mouse or by using the keyboard to mimic a mouse, referred to as mouse keys. Touch-sensitive screens can be used in many devices, including notebooks, kiosks, and mobile devices. Such devices can detect the presence and location of a touch or multiple touches through several means, among them: capacitive sensing and resistive sensing. Keyboard actions can allow the user to enter data while in setup context, tab through entries, and choose multiple items, etc. Other types of input devices, such as haptic-enabled devices can be used.

The components of the DAS 100 can be physically connected prior to user involvement via the GUI. If the components 102-130 are powered on, then the software in the various components 102-130 can determine information regarding the incoming signals that it detects, thus allowing the signal inputs to be automatically configured. Intervention on the part of the user may not be necessary to set up the system 100 in many cases. The incoming sources, however, may be associated with the necessary destinations for the signals to be propagated across the system as planned. This is a task that can be difficult to automate because too many assumptions may be made. This is a task typically requiring user configuration. By using a combination of visual cues and user action support, it may be possible to provide a simple, intuitive tool that will allow the user who is not an expert user to successfully complete this task in a few easy steps.

Associations may be made via drag and drop operations or by a guided, set of steps using the methods discussed above.

FIG. 9 depicts a process flow diagram for configuring the DAS based on the user instructions according to one aspect of the present disclosure. Signal transport information 902, hardware identification information 904, and other information or parameters of the DAS 906 may be sent from the DAS controller 132 to the computing device 102. The computing device 102 may use the signal transport information 902, the hardware identification information 904, and other information 906 to generate a signal distribution interface and a signal set assignment user interface at process 908.

As described above, the signal distribution interface may include displaying or otherwise presenting to the user 900 a first grouping of one or more widgets, where each widget represents a headend component, such as a CAN, of the DAS. A second grouping of one or more widgets representing one or more remote units in the DAS that are associated with a headend component of the first grouping. The signal distribution interface may also include a list of signal sets representing groups of signals to be transported in the DAS. A general alarm indicator representing an alarm status for all hardware components in the DAS may also be provided. Individual alarm indicators representing an alarm status for individual hardware components or groups of hardware components in the DAS may be provided in addition to the general alarm indicator. The signal distribution interface may also include tabs for switching between user contexts, such as an operational context whereby the user can view events and alarms, view signal status, or update software and a setup context whereby the user can edit alarm settings, set hardware component parameters, or associate signal sources with hardware components. The signal distribution interface may also include crumb trails for indicating a location or attribute of a currently displayed screen face.

The signal set assignment user interface may include a list of signals transported by a DAS and a list of editable signal sets. Each signal set includes one or more of the signals that are transported by the DAS. Signals can be assigned to a signal set by various user interface means. For example, a signal can be dragged and dropped onto a desired signal set or can be selected and a separate button may be activated in order to associate the signal with a signal set.

The computing device may output the signal distribution interface and the signal set assignment interface as audiovisual data for display on a computer at process 910. The computer may include a variety of input/output means for receiving mouse actions or touch actions such as single-clicking, double-clicking, click-holding, click-releasing, single finger touch, and multi-finger touch.

At process 912, the user 900 may initiate a request to associate a signal set with a hardware component via the signal distribution interface. For example, as described above with respect to FIG. 5, the signal set S2 can be associated with the UAP.1 by a user dragging the representation 502 of the signal set to the representation 504 of the UAP listed at the top of the screen face 500.

In response to receiving the request 912, the computing device 102 may generate instructions, at process 914, for configuring the DAS controller 132 to provide the signals in the signal set identified by the request 912 to the hardware component also identified by the request 912. For example, the computing device 102 may configure the DAS controller 132 to route signals associated with the signal set S2 to the hardware component UAP.1. The instructions generated at process 914 may be provided at process 916 to the DAS controller 132 for execution.

The foregoing description of the examples, including illustrated examples, of the invention has been presented only for the purpose of illustration and description and is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Numerous modifications, adaptations, and uses thereof will be apparent to those skilled in the art without departing from the scope of this invention. The illustrative examples described above are given to introduce the reader to the general subject matter discussed here and are not intended to limit the scope of the disclosed concepts. 

What is claimed is:
 1. A system, comprising: a processor device; and a non-transitory computer-readable medium on which a signal distribution engine is stored and which is executable by the processor device for: receiving information about signals transported by a distributed antenna system (DAS) and about hardware components of the DAS that include a headend component and a remote component; generating a signal set assignment user interface that includes a representation of signals transported by the system and a representation of signal sets that include the signals transported by the system; generating a signal distribution user interface that includes representations of signal sets, hardware components, and associations between the signal sets and the hardware components; and responsive to receiving a command via the signal distribution user interface to associate a signal set with a specified hardware component, outputting a command to cause the DAS to configure a signal path so that signals in the signal set are provided to the specified hardware component.
 2. The system of claim 1, wherein the signal distribution engine is executable by the processor for generating the signal distribution user interface that includes an indicator of an alarm condition.
 3. The system of claim 1, wherein the signal distribution user interface includes: an operational context in which events and alarms are viewable, signal status is viewable, or options for updating software are viewable; and a setup context in which alarm settings are editable, hardware component parameters are received, or signal sources are associated with hardware components.
 4. The system of claim 3, wherein the system is switchable between the operational context and the setup context.
 5. The system of claim 3, wherein the signal distribution engine is executable by the processor for generating the signal distribution user interface that includes generating a context-dependent grouping of visual cues based on whether the system is operating in the operational context or the setup context.
 6. The system of claim 3, wherein the signal distribution engine is executable by the processor for generating the signal distribution user interface that includes generating visual cues wherein a location of the visual cues is independent of the context in which the system is operating.
 7. The system of claim 1, wherein the signal distribution user interface includes: a first list of signal sets transported by the system, the list of signal sets being positioned in a first pane; a list of zones in the system and a second list of signals sets associated with each zone, the list of zones and the second list of signals sets being positioned in a second pane, wherein at least one of the zones is selectable; and a list of remote units associated with a selected zone and a third list of signal sets associated with the selected zone, the list of remote units and the third list of signal sets being positioned in a third pane.
 8. A method, the method comprising: receiving information about signals transported by a distributed antenna system (DAS); receiving identification and parameters from the controller in the DAS about hardware components of the DAS that include at least a headend component and a remote component; generating a signal set assignment user interface that includes a list of signals transported by the system and a signal set formation area for receiving one or more signals constituting a signal set; generating a signal distribution user interface that includes representations of signal sets, hardware components, and associations between the hardware components; and responsive to receiving a command via the signal distribution user interface to associate the signal set to a specified hardware component, outputting a command to the controller to cause the DAS to configure a signal path so that signals in the signal set are provided to the specified hardware component.
 9. The method of claim 8, further comprising providing an indicator of an alarm condition in the signal distribution user interface.
 10. The method of claim 8, wherein generating the signal distribution user interface further includes: providing an operational context in which current events and alarms are viewable, signal status is viewable, and options for updating software are viewable; and providing a setup context in which alarm settings are editable, hardware component parameters are received, or signal sources are associated with hardware components.
 11. The method of claim 10, further comprising generating visual cues, in the signal distribution user interface, that are located independent of the context in which the system is operating.
 12. The method of claim 10, further comprising generating representations of components in the distributed antenna system, in the signal distribution user interface, that are grouped based on whether the system is operating in the operational context or the setup context.
 13. A signal distribution user interface, comprising: a first pane that includes a representation of signal sets transported by a distributed antenna system; and a second pane that includes a representation of hardware components in the distributed antenna system and a representation of associations between the signal sets and the hardware components in the distributed antenna system, wherein the signal distribution user interface is configured to respond to receiving a command to associate a signal set with a specified hardware component by outputting a command to cause the distributed antenna system to configure a signal path to allow signals in the signal set to be provided to the specified hardware component, wherein the user interface is configured to be generated by a processor device executing a signal distribution engine stored on a non-transitory computer-readable medium.
 14. The signal distribution user interface of claim 13, wherein the signal distribution user interface is configured to receive the signal sets from a signal set assignment user interface, where the signal set assignment user interface is configured to display an available signals pane that includes a representation of signals transported by the distributed antenna system that are available to be assigned to a signal set, and an assigned signals pane that includes a representation of signal sets transported by the distributed antenna system.
 15. The signal distribution user interface of claim 13, wherein the second pane is further configured to display a list of zones in the system and signal sets associated with the zones, where the signal distribution user interface is configured to display a third pane displaying a list of remote units and signal sets associated with the remote units, the third pane being configured to display a zone selected from among the list of zones displayed in the second pane.
 16. The signal distribution user interface of claim 15, wherein the signal distribution user interface is further configured to display: an operational context in which current events and alarms are viewable, signal status is viewable, and options for updating software are viewable; and a setup context in which alarm settings are editable, hardware component parameters are received, or signal sources are associated with hardware components.
 17. The signal distribution user interface of claim 16, wherein a location of the first pane, the second pane, and the third pane is based on whether the system is operating in the operational context or the setup context.
 18. The signal distribution user interface of claim 16, wherein a location of the first pane, the second pane, and the third pane is independent of the context in which the system is operating.
 19. The signal distribution user interface of claim 16, further comprising a signal distribution user interface configured to be displayable on a display device, the signal distribution user interface being configured to display: a first grouping of one or more visual cues, each visual cue representing a headend component of a distributed antenna system (DAS); a second grouping of one or more visual cues, each visual cue representing one or more remote units in the DAS associated with a headend component of the first grouping; and a list of signal sets, each signal set representing a group of signals to be transported in the DAS.
 20. The signal distribution user interface of claim 19, further comprising a general alarm indicator representing an alarm status for all hardware components in the DAS and an individual alarm indicator representing an alarm status for an individual hardware component or a group of hardware components in the DAS. 